-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission deconstruction #800
Conversation
Thanks for the PR @zprebosnyak-lm! There are a few test failures:
Also, could you please sign-off your commits so the DCO check passes? You can find instructions by clicking on the Details link next to the failing build check. |
* feat: add upstream MR creation * Deleted .gitlab-ci.yml * fix: build & push api server with kaniko * fix: address prior stage error * fix: fix dockerfile path * fix: run maven build job * fix: switch to mvn version eclipse 21 * fix: address java cacert path * fix: switch java jdk 17 * fix: add the settings.xml file * fix: added additonal script to create jar * fix: build apiserver docker container * remove crane job * create target destination file * remove target dir * disable the kaniko before script * fix: add back before script to copy target file * commented target from dockerignore * revise docker build context * move logback-json to root * move back logback-json * switch dockerfile to original proxy cached * applied suggested changes * revert to rule to default branch * test: see if logic works with existing permissions * test: revert old permissions test, test case with new permissions * fix: copy pasta'd myself * feat: add new permissions to API routes * fix: change api permission to match CRUDops better * fix: change policy condition resource for update * test: add api and ci changes * test: yq command * test: yq cmd * test: if its the container * test: parse version * test: why is it connecting to proxy * test: use curl * fix: cleanup CI * test: cleanup pt2 * fix: clean pt3 * fix: spelling mistake in description * fix: revert some files and change values back to original --------- Co-authored-by: e407773 <[email protected]> Co-authored-by: Cortes, Noel <[email protected]> Signed-off-by: Zachary Prebosnyak <[email protected]>
Signed-off-by: Zachary Prebosnyak <[email protected]>
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences🚀 Don’t miss a bit, follow what’s new on Codacy. Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
@nscuro Thanks for pointing that out, both PRs commits are signed, linting, and tests are now passing. |
Thanks @zprebosnyak-lm, looks good to me! Unfortunately we have another pending PR that conflicts with this one: #785 Judging by the PR size alone, I think it makes sense to get that one merged first, and then resolve conflicts in you PR, rather than the other way around. The change in Swagger annotations makes the other PR a tad harder to deal with... Not a pretty situation, and in worst case we can take care of resolving those conflicts for you. Does that sound alright? |
Hey @nscuro, yeah that sounds good. I'll watch for that to be merged, just curious is there a timeline for merging that PR? |
It only has a few minor remarks pending, I'm hoping to get it merged tomorrow. |
@zprebosnyak-lm The PR is merged now. Again apologies for the inconvenience. |
@nscuro No worries! The conflicts should all be resolved now |
Build failure is fixed via #818. If you merge |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences🚀 Don’t miss a bit, follow what’s new on Codacy. Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 🙌
Description
Frontend changes in PR 103
This PR breaks down the current permissions set to align with the CRUD operations that each permission can perform through the API. It retains the original permissions to stay backwards compatible. The original permissions are a top level permission that can perform all the CRUD operations the broken down permissions can.
Updated permission set:
Addressed Issue
Fixes Issue 1406
Additional Details
Implemented this change to be leveraged with the ACL as it continues to develop. Allowing more granular permission assignment would let admins assign various roles to users such as an owner, developer, or viewer having different levels of access to the same projects.
Checklist